session module
am 29.10.2010 07:43:21 von Jeff Pangis Apache::Session or CGI::Session better for mod_perl?
Thanks.
is Apache::Session or CGI::Session better for mod_perl?
Thanks.
Both work. CGI::Session was better maintained for a while but it
looks like Apache::Session has been updated recently. Pick the one
that you find easiest to understand from the documentation.
- Perrin
2010/10/29 Jeff Pang
> is Apache::Session or CGI::Session better for mod_perl?
>
> Thanks.
>
try a framework. that's much more popular. :)
On Fri, Oct 29, 2010 at 8:20 PM, Perrin Harkins
> Both work. Â CGI::Session was better maintained for a while but it
> looks like Apache::Session has been updated recently. Â Pick the one
> that you find easiest to understand from the documentation.
>
> - Perrin
>
> 2010/10/29 Jeff Pang
>> is Apache::Session or CGI::Session better for mod_perl?
>>
>> Thanks.
>>
>
--=20
Fayland Lam // http://www.fayland.org/
äº 2010-10-29 20:28, Fayland Lam åé:
> try a framework. that's much more popular. :)
>
I wrote a small application with few scripts.
A framework like catalyst is too large to use for me.
Thanks.
Jeff.
äº 2010-10-29 20:20, Perrin Harkins åé:
> Both work. CGI::Session was better maintained for a while but it
> looks like Apache::Session has been updated recently. Pick the one
> that you find easiest to understand from the documentation.
>
I know CGI::Session well.
But have been thinking does Apache::Session get better performance under
modperl?
Thanks.
Jeff.
try Dancer. which is very suitable for small application. just one file.
Thanks
On Fri, Oct 29, 2010 at 8:37 PM, Jeff Pang
> äº=8E 2010-10-29 20:28, Fayland Lam åé:
>>
>> try a framework. that's much more popular. :)
>>
>
> I wrote a small application with few scripts.
> A framework like catalyst is too large to use for me.
> Thanks.
>
> Jeff.
>
>
--=20
Fayland Lam // http://www.fayland.org/
On Fri, Oct 29, 2010 at 8:39 AM, Jeff Pang
> I know CGI::Session well.
> But have been thinking does Apache::Session get better performance under
> modperl?
I haven't measured it, but I doubt there's any significant performance
difference. Don't be fooled by the "CGI" in CGI::Session.
- Perrin
äº 2010-10-29 20:42, Fayland Lam åé:
> try Dancer. which is very suitable for small application. just one file.
>
Ok I will check out it.
I first time knew Dancer from ruby 2 years ago.
Never know that there is a perl execution of that.
--0016e6dee6d6dcd8790493c73a20
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Haven't used any of the popular session modules in awhile.
Are these susceptible to the cleartext cookie silliness exposed by
FireSheep?
"Great Artists Ship"
Lon Koenig lon@schnoggo.com http://lonk.me
On Fri, Oct 29, 2010 at 7:47 AM, Jeff Pang
> äº=8E 2010-10-29 20:42, Fayland Lam åé:
>
> try Dancer. which is very suitable for small application. just one file.
>>
>>
> Ok I will check out it.
> I first time knew Dancer from ruby 2 years ago.
> Never know that there is a perl execution of that.
>
>
--0016e6dee6d6dcd8790493c73a20
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Haven't used any of the popular session modules in awhile.
Are these=
susceptible to the cleartext cookie silliness exposed by FireSheep?
>
yle=3D"color: rgb(0, 0, 0);">Lon Koenig  Â
lto:lon@schnoggo.com" target=3D"_blank">lon@schnoggo.com
color: rgb(0, 0, 0);">Â
=3D"_blank">http://lonk.me
h=3D"1">
0 at 7:47 AM, Jeff Pang <
ina.com">jeff_pang@sina.com> wrote:
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">äº=8E 2010-10=
-29 20:42, Fayland Lam åé:
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
try Dancer. which is very suitable for small application. just one file.
>
Ok I will check out it.
I first time knew Dancer from ruby 2 years ago.
Never know that there is a perl execution of that.
--0016e6dee6d6dcd8790493c73a20--
--- On Fri, 10/29/10, Fayland Lam
> try Dancer. which is very suitable
> for small application. just one file.
One file containing:
"""
use Dancer::Config;
use Dancer::FileUtils;
use Dancer::GetOpt;
use Dancer::Error;
use Dancer::Helpers;
use Dancer::Logger;
use Dancer::Plugin;
use Dancer::Renderer;
use Dancer::Response;
use Dancer::Route;
use Dancer::Serializer::JSON;
use Dancer::Serializer::YAML;
use Dancer::Serializer::XML;
use Dancer::Serializer::Dumper;
use Dancer::Session;
use Dancer::SharedData;
use Dancer::Handler;
use Dancer::ModuleLoader;
"""
which isn't "one file" by my reckoning. Nevertheless, it looks very interes=
ting. I will try a toy applet with it this weekend. Thanks for mentioning i=
t.
Phil
> On Fri, Oct 29, 2010 at 8:37 PM, Jeff Pang
> wrote:
> > äº=8E 2010-10-29 20:28, Fayland Lam åé:
> >>
> >> try a framework. that's much more popular. :)
> >>
> >
> > I wrote a small application with few scripts.
> > A framework like catalyst is too large to use for me.
=0A
On Fri, Oct 29, 2010 at 4:23 PM, Lon Koenig
> Are these susceptible to the cleartext cookie silliness exposed by FireSheep?
Well, Apache::Session doesn't handle cookies at all, so it's entirely
up to you how you want to deal with it, and CGI::Session doesn't
dictate whether or not your site uses SSL, so that is also up to you.
There is no way to prevent people from potentially seeing cookies (or
anything else) passed over a non-SSL network. Sites that are
seriously concerned about this should use SSL. Even sites that don't
use SSL should use cookies with some form of MAC and a reasonable
session timeout.
- Perrin